[release/5.0] use main branch for publishing#7071
Merged
riarenas merged 1 commit intodotnet:release/5.0from Mar 9, 2021
Merged
[release/5.0] use main branch for publishing#7071riarenas merged 1 commit intodotnet:release/5.0from
riarenas merged 1 commit intodotnet:release/5.0from
Conversation
Contributor
Author
|
@mmitche @markwilkie @epananth friendly ping |
mmitche
approved these changes
Mar 9, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Use the main branch as the publishing branch in reaction to the renaming of the default branch in arcade: https://github.com/dotnet/core-eng/issues/12145
Customer Impact
The master branch will be deleted from azure devops in a couple of weeks, so publishing will fail.
Regression
No
Risk
Low. The main branch already exists in azure devops and is the only branch that will stay up to date.
Workarounds
None